Crate abi_stable
source ·Expand description
For Rust-to-Rust ffi, with a focus on creating libraries loaded at program startup, and with load-time type-checking.
This library allows defining Rust libraries that can be loaded at runtime, even if they were built with a different Rust version than the crate that depends on it.
These are some usecases for this library:
-
Converting a Rust dependency tree from compiling statically into a single binary, into one binary (and potentially) many dynamic libraries, allowing separate re-compilation on changes.
-
Creating a plugin system (without support for unloading).
Features
Currently this library has these features:
-
Features the
sabi_trait
attribute macro, for creating ffi-safe trait objects. -
Ffi-safe equivalent of some trait objects with
DynTrait
. -
Provides ffi-safe alternatives/wrappers for many standard library types, in the
std_types
module. -
Provides ffi-safe wrappers for some types defined in external crates, in the
external_types
module. -
Provides the
StableAbi
trait for asserting that types are ffi-safe. -
The prefix types feature for building extensible modules and vtables, without breaking ABI compatibility.
-
Supports ffi-safe nonexhaustive enums, wrapped in
NonExhaustive
. -
Checking at load-time that the types in the dynamic library have the expected layout, allowing for semver compatible changes while checking the layout of types.
-
Provides the
StableAbi
derive macro to both assert that the type is ffi compatible, and to get the layout of the type at load-time to check that it is still compatible.
Examples
For examples of using abi_stable
you can look at the readme example,
or for the crates in the examples directory in the repository for this crate.
This crate also has examples in the docs for most features.
To run the example crates you’ll generally have to build the *_impl
crate,
then run the *_user
crate (all *_user
crates should have a help message and a readme.md).
Minimum Rust version
This crate support Rust back to 1.46.0
You can manually enable support for Rust past 1.46.0 with the rust_*_*
cargo features.
Had to bump the MSRV from 1.41.0 to 1.46.0 because fixing Rust nightly compatibility caused Internal Compiler Errors in older Rust versions.
Crate Features
These are default cargo features that enable optional crates :
-
“channels”: Depends on
crossbeam-channel
, wrapping channels from it for ffi inabi_stable::external_types::crossbeam_channel
. -
“serde_json”: Depends on
serde_json
, providing ffi-safe equivalents of&serde_json::value::RawValue
andBox<serde_json::value::RawValue>
, inabi_stable::external_types::serde_json
.
To disable the default features use:
[dependencies.abi_stable]
version = "<current_version>"
default-features = false
features = [ ]
enabling the features you need in the features
array.
Manually enabled
These are crate features to manually enable support for newer language features:
-
“rust_1_51_0”: Enables impls which require using const generics, including implementing StableAbi for arrays of all lengths, requires Rust Rust 1.51.0 or higher.
-
“rust_latest_stable”: Enables the “rust_1_*” features for all the stable releases.
Glossary
interface crate
:the crate that declares the public functions, types, and traits that
are necessary to load the library at runtime.
ìmplementation crate
:A crate that implements all the functions in the interface crate.
user crate
:A crate that depends on an interface crate
and
loads 1 or more ìmplementation crate
s for it.
module
:refers to a struct of function pointers and other static values.
The root module implement the RootModule
trait.
These are declared in the interface crate
,exported in the implementation crate
,
and loaded in the user crate
.
Rust-to-Rust FFI types.
Types must implement StableAbi
to be safely passed through the FFI boundary,
which can be done using the StableAbi
derive macro.
For how to evolve dynamically loaded libraries you can look at the library_evolution module.
These are the kinds of types passed through FFI:
-
Value kind:
This is the default kind when deriving StableAbi. The layout of these types must not change in a minor versions. -
Nonexhaustive enums :
Enums wrapped insideNonExhaustive
, which can add variants in minor versions of the library. -
Trait objects :
Trait object-like types generated using thesabi_trait
attribute macro, which erase the type of the value they wrap,implements the methods of the trait, and can only be unwrapped back to the original type in the dynamic library/binary that created it. -
Opaque kind:
Types wrapped inDynTrait
, whose layout can change in any version of the library, and can only be unwrapped back to the original type in the dynamic library/binary that created it. -
Prefix types :
Types only accessible through some custom pointer types, most commonly vtables and modules, which can be extended in minor versions while staying ABI compatible, by adding fields at the end.
Extra documentation
-
Unsafe code guidelines :
Describes how to write unsafe code ,relating to this library. -
Troubleshooting :
Some problems and their solutions.
Macros (derive and attribute)
-
sabi_trait
attribute macro:
For generating ffi-safe trait objects. -
StableAbi
derive :
For asserting abi-stability of a type, and obtaining the layout of the type at runtime. -
Nonexhaustive enums :
Details for how to declare nonexhaustive enums. -
Prefix types (using the StableAbi derive macro):
The method by which vtables and modules are implemented, allowing extending them in minor versions of a library.
Re-exports
pub use abi_stable::sabi_types::RMut;
pub use abi_stable::sabi_types::RRef;
pub use crate::erased_types::InterfaceBound;
Modules
InlineStorage
trait,and related items.#[sabi_trait]
attribute.Macros
Tuple*
with the types passed to the macro.RootModule::root_module_statics
associated function.extern fn
correctly.TypeInfo
for some type.ItemInfo
, with information about the place where it’s called.NulStr
from a string literal,
truncating the string on internal nul bytes.VersionStrings
with the
major.minor.patch version of the library where it is invoked.abi_stable::std_types::Tuple*
with the values passed to the macro.Tag
,
a dynamically typed value for users to check extra properties about their types
when doing runtime type checking.CompGenericParams
,
when manually implementing StableAbi
.Copy
generic types that are the same concrete type.Structs
Statics
Traits
implementation type
,
with an associated InterfaceType
which describes the traits that
must be implemented when constructing a DynTrait
from Self
,
using the DynTrait::from_value
and DynTrait::from_ptr
constructors,
so as to pass an opaque type across ffi.DynTrait<Pointer<()>, ThisInterfaceType>
.Attribute Macros
implementation crate
.sabi_extern_fn
attribute macro allows defining extern "C"
function that
abort on unwind instead of causing undefined behavior.Derive Macros
GetStaticEquivalent
macro derives the GetStaticEquivalent_
trait.